Skip to content

Conversation

@smoelius
Copy link
Member

Implements #605

@smoelius
Copy link
Member Author

Commit 398a449 is published to crates.io as 0.16.0-rc.0 if folks want to try it out.

@vanhauser-thc
Copy link
Contributor

$ cargo afl config --update
Cloning into '/home/user/.local/share/afl.rs/AFLplusplus'...
remote: Enumerating objects: 43539, done.
remote: Counting objects: 100% (4012/4012), done.
remote: Compressing objects: 100% (409/409), done.
remote: Total 43539 (delta 3821), reused 3604 (delta 3603), pack-reused 39527 (from 2)
Receiving objects: 100% (43539/43539), 32.83 MiB | 35.50 MiB/s, done.
Resolving deltas: 100% (32144/32144), done.
Note: switching to 'origin/stable'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at eadc8a2a Merge pull request #2530 from AFLplusplus/dev

thread 'main' (898359) panicked at /home/marc/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/cargo-afl-0.16.0-rc.0/src/main.rs:145:34:
called `Result::unwrap()` on an `Err` value: could not run 'make clean install' in /home/marc/.local/share/afl.rs/AFLplusplus
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

as make clean install works in '/home/user/.local/share/afl.rs/AFLplusplus' my guess is the working directory is wrong when executing make?

And I propose to add --dev => $ cargo afl config --update --dev to checkout the dev branch

@smoelius
Copy link
Member Author

as make clean install works in '/home/user/.local/share/afl.rs/AFLplusplus' my guess is the working directory is wrong when executing make?

Could I impose on you to cargo afl config --update --force --verbose and paste output (minus anything sensitive)?

And I propose to add --dev => $ cargo afl config --update --dev to checkout the dev branch

I just tested and it appears --tag dev works. Could that suffice?

@vanhauser-thc
Copy link
Contributor

Sorry, I had not see the --tag parameter. that works, thanks :)

I tried the command you asked me - and now it works. I have installed a newer rust toolchain in between though. But this should not have changed anything for compiling AFL++. weird.

@smoelius
Copy link
Member Author

I tried the command you asked me - and now it works. I have installed a newer rust toolchain in between though. But this should not have changed anything for compiling AFL++. weird.

Thanks very much for testing and please let me know if the problem arises again! 🙏

@smoelius smoelius force-pushed the implement-605 branch 2 times, most recently from 2439548 to 48baec7 Compare September 29, 2025 13:32
@smoelius smoelius force-pushed the implement-605 branch 2 times, most recently from f3ccf89 to 5be84e4 Compare October 13, 2025 11:34
@smoelius smoelius added this pull request to the merge queue Oct 31, 2025
Merged via the queue into master with commit f3250c5 Oct 31, 2025
19 checks passed
@smoelius smoelius deleted the implement-605 branch October 31, 2025 22:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Proposal to change how cargo-afl manges AFL++ source code

3 participants